Overview of operation: Control Loop Data

Use this operation to import cached control loop data from deployed CSense Process+ control loops.

Properties

Category:	Import
Performance risk:	Potentially high performance risk. The combination of selected loops and selected loop attributes may result in a dataset that exceeds the maximum number of columns. Larger time windows will result in large datasets.
Knowledge required:	None

Effect on datasets

How many datasets are required to perform this operation?	None
Does it create a new dataset?	Yes
Can you reconfigure this operation?	Yes
Can you apply this operation to a locked dataset?	NA
Does it modify the current dataset in any way?	NA

Requirements

Deployed Process+ Loops.

Results

A new dataset with the control loop data that you selected while configuration is created. The resulting dataset will have tags that you selected for each loop as columns. For example, if there are two loops namely, Loop1 and Loop2, and you selected Tag_PV and Tag_UL for both the loops, the resulting dataset will have four columns as follows:

Timestamp Loop1_Tag_PV Loop1_Tag_UL Loop2_Tag_PV Loop2_Tag_UL

Common errors

While you import the cached control loop data, you might encounter the following errors:

Exceeded the column selection limit

When you select too many loops or tags and exceed the column selection limit, the Number of columns in resulting dataset notification changes to red.

If you hover over the notification, you will see the Maximum number of columns exceeded. Reconfigure the operation to reduce the number of columns in the resulting dataset tooltip.

You must select the loops or tags such that the columns in the resulting dataset will not exceed the limit.

The selected loop does not have any loop data

If you select a loop and if the selected loop does not have any data, the resulting dataset will have empty values.

You must ensure that the loops that you selected have data for the timestamp that you configured.